Hi,I teseted Exchange 2007 AutoDiscover servicewithtest-OutlookWebservice command and getresponse below: Id : 1003Type : InformationMessage : About to test AutoDiscover with the e-mail address Michael@chicken.com. Id : 1006Type : InformationMessage : The Autodiscover service was contacted at https://SRV-EX.egg.local/Autodiscover/Autodiscover.xml. Id : 1016Type : SuccessMessage : [EXCH]-Successfully contacted the AS service at https://srv-ex.egg.local/EWS/Exchange.asmx. The elapsed time was 15 milliseconds. Id : 1015Type : SuccessMessage : [EXCH]-Successfully contacted the OAB service at https://srv-ex.egg.local/EWS/Exchange.asmx. The elapsed time was 0 milliseconds. Id : 1014Type : SuccessMessage : [EXCH]-Successfully contacted the UM service at https://srv-ex.egg.local/UnifiedMessaging/Service.asmx. The elapsed time was 15 milliseconds. Id : 1016Type : InformationMessage : [EXPR]-The AS is not configured for this user. Id : 1015Type : SuccessMessage : [EXPR]-Successfully contacted the OAB service at . The elapsed time was 0 milliseconds. Id : 1014Type : InformationMessage : [EXPR]-The UM is not configured for this user. Id : 1017Type : SuccessMessage : [EXPR]-Successfully contacted the RPC/HTTP service at https://mail.egg.com/Rpc. The elapsed time was 0 milliseconds. Id : 1006Type : SuccessMessage : The Autodiscover service was tested successfully.My questions are:First, the "AS" stands for Availability Service or Autodiscover Service?Second, if AS is for Availability Service, how am I able toconfigure it for this user (or all users)?Thanks

Hi,In event id 1016, AS is Availability Service.Did you configured Autodiscover Service properly as per below article? Speciallyinternalurl & externalurl with Set-WebServicesVirtualDirectory...How to Configure Exchange Services for the Autodiscover Servicehttp://technet.microsoft.com/en-us/library/bb201695.aspxAmit Tank | MVP - Exchange | MCITP:EMA MCSA:M | http://ExchangeShare.WordPress.com

Hi Amit, I actually fixed it yesterday. Just as you mentioned, externalUrl was missing for WebServiceVirtualDirectory. Just share a bit more of my fix, you actually have to put the internal FQAN in the "externalUrl".I initially put our public domain into the externalUrl, but it didn't work. e.g. You have to put as https://srv-ex.egg.local/EWS/Exchange.asmx instead of https://mail.chiken.com/EWS/Exchange.asmx as EWS VD won't allow direct access from public. The other thing is you may have to wait for 10-15mins to allow Exchange to apply the changes.

Cool, thanks for the sharing additional information...Amit Tank | MVP - Exchange | MCITP:EMA MCSA:M | http://ExchangeShare.WordPress.com

Hi aha_tom and Amit, I am new to Exchange Server 2007.I have fixedthe problemlike Amit's suggestion. this works instantanously.Ihave another question about external relay connector. if i want to send and receive email from everyone on the internet and don't let the others use my server for relay agent. Will i have to use blocked and allowed sender list fromproviders on the internet ?ThanksVu Binh

On Sat, 12-Sep-09 14:16:48 GMT, vbsg wrote:>>>Hi aha_tom and Amit, I am new to Exchange Server 2007.I have fixed the problem like Amit's suggestion . this works instantanously.I have another question about external relay connector. if i want to send and receive email from everyone on the internet and don't let the others use my server for relay agent. Will i have to use blocked and allowed sender list from providers on the internet ?ThanksVu Binh not configured to be used as SMTPrelay server by anonymous connections. Anonymous connections arepermitted to send email /to/ your server provided the recipient'sdomain is in the 'accepted domains' list. You can further restrictthat so only email addresses that are present in your AD will beaccepted (this is a 'best practice').You server probably already has a "Send Connector" that will useanonymous connections to send email directly to other SMTP servers.In general, there's no need to use connection filtering. In practice,however, many organizations use a DNSBL to refuse connections from IPaddresses that the DNSBL operator has deemed to be a problem (checkthe DNSBL policy on how that decision is made and whether you caninteract with the DNSBL operator to 'delist' IP addresses -- it's notat all uncommon to find your customers IP addresses on these lists).---Rich MatheisenMCSE+I, Exchange MVP--- Rich Matheisen MCSE+I, Exchange MVP